after or before the dash, since I don't
> like it to stick to some letters like "o").
Just consider that you should add an horizontal box (or pair both space
and hyphen), otherwise you may get a line break between character and
hyphen (instead of the hair space):
\starttext
\start
by that ... context can add profiles if
configured to do so (best not to embed them) ... and why should there be
a profile anyway ... crappy arguments .. especially because when i run
\usemodule[tikz]
\startTEXpage
\definecolor [colorone] [r=0,g=0,b=0.5]
\definecolor [colortwo] [c=0,m=1
t,depth=\strutdp,offset=.250ex,color=red]
\definebar
[yourbar]
[backgroundbar]
[height=\strutht,depth=\strutdp,offset=.125ex,color=blue]
\definebar
[ourbar]
[backgroundbar]
[height=\strutht,depth=\strutdp,offset=.125ex,color=green]
\starttext
\startTEXpage[width=4cm]
\startformul
normalization on the
way]):
\definefontfamily[mainface][rm][EBGaramond]
\setupbodyfont[mainface, 500pt]
\definecolor [tred] [r=1,t=.5,a=1]
\definecolor [tblue] [b=1,t=.25,a=1]
\starttext
\startTEXpage[offset=1ex]
\startoverlay
{\color[tred]{Ά}}
{\color[tblue]{Ά}}
\stopoverlay
},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d
},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d
: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only
, quality}},
bf={style: regular, features:{default, boldened-30}},
bi={style: regular, features:{default, boldened-30, slanted}}]
\setupbodyfont
[mainface, 30pt]
\starttext
\startTEXpage[offset=1ex]
a
{\it a}\\
{\bf a}
{\bi a}
\stopTEXpage
\stoptext
}},
bi={style: regular, features:{default, boldened-30, slanted}}]
\setupbodyfont
[mainface, 30pt]
\starttext
\startTEXpage[offset=1ex]
a
{\it a}\\
{\bf a}
{\bi a}
\stopTEXpage
\stoptext
With current latest (2024.02.27 09:21), LuaTeX gets boldened and slanted
for regular
On Feb. 19 2024, at 2:39 pm, Mikael Sundqvist wrote:
> Hi,
>
> Try
> \startTEXpage[pagestate=start]
> /Mikael
> On Mon, Feb 19, 2024 at 2:31 PM Emanuel Han via ntg-context
> wrote:
> >
> > I just made a strange observation in the output pdf of the attached
>
Hi,
Try
\startTEXpage[pagestate=start]
/Mikael
On Mon, Feb 19, 2024 at 2:31 PM Emanuel Han via ntg-context
wrote:
>
> I just made a strange observation in the output pdf of the attached
> layer_set.tex, which is that when opening it with a pdf viewer like skim or
> m
. And then do\dorecurse{5}{\startTEXpage[offset=1DK]\useMPgraphic{layerset#1}\stopTEXpage}if that is the looping you are after./MikaelOn Fri, Feb 16, 2024 at 6:54 AM Emanuel Han via ntg-context wrote:>> Resp. the solution should be such that each generated PDF page has the same dimension, th
ot sure I get what you are missing. But you can try
> setbounds currentpicture to (fullsquare scaled 200) ;
> in base. And then do
> \dorecurse{5}{
> \startTEXpage[offset=1DK]
> \useMPgraphic{layerset#1}
> \stopTEXpage
> }
>
> if that is the looping you are after.
> /M
Hi,
not sure I get what you are missing. But you can try
setbounds currentpicture to (fullsquare scaled 200) ;
in base. And then do
\dorecurse{5}{
\startTEXpage[offset=1DK]
\useMPgraphic{layerset#1}
\stopTEXpage
}
if that is the looping you are after.
/Mikael
On Fri, Feb 16, 2024 at 6:54 AM
aphic{base}
> > > z1 = origin ;
> > > z2 = (10,50) ;
> > > z3 = (40,30) ;
> > >
> > > picture layerA;
> > > layerA:=image(
> > > label("Word 1", z1);
> > > );
> > >
> > > picture layerW;
> > > layerW:
;
> > layerW:=image(
> > label("Mot 2", z2);
> > );
> >
> > picture layerM;
> > layerM:=image(
> > label("Parola 3", z3);
> > );
> >
> > picture layerC;
> > layerC:=image(
> > label("Wort 4", z3
icture layerC;
> layerC:=image(
> label("Wort 4", z3+z1);
> );
>
> picture layerY;
> layerY:=image(
> label("Nummer 5", z2+z3);
> );
>
> picture layerU;
> layerU:=image(
> label("number 6", z2+z1);
> );
> \stopuseMPgraphic
>
rtuseMPgraphic{layerset2}
\includeMPgraphic{layerset1} ;
draw layerY ;
\stopuseMPgraphic
\startuseMPgraphic{layerset3}
\includeMPgraphic{layerset2} ;
\includeMPgraphic{Gamma} ;
\stopuseMPgraphic
\startuseMPgraphic{layerset4}
\includeMPgraphic{layerset2} ;
draw layerU ;
\stopuseMPgraphic
\startu
Hi Hans,
I have the following sample which behaves differently after latest from
2023.09.26 18:19:
\definetweakedfont[wider][xscale=1075]
\starttext
\startTEXpage[align=center]
\contextversion\\
\wider \contextversion
\stopTEXpage
\stoptext
Up to that version
rescripts:
\startTEXpage[offset=1DK]
\m{1 - {}^nC_2\tan^2\theta + {}^nC_4 }
\m{1 - C_2^^n \tan^2\theta + C_4^^n }
\stopTEXpage
If you want them below, use double _.
/Mikael
On Mon, Jan 15, 2024 at 7:45 AM Shiv Shankar Dayal
mailto:shivshankar.da...@gmail.com>
Thanks a lot Mikael.
On Mon, Jan 15, 2024 at 12:24 PM Mikael Sundqvist wrote:
> Hi,
>
> ConTeXt supports prescripts:
>
> \startTEXpage[offset=1DK]
>
> \m{1 - {}^nC_2\tan^2\theta + {}^nC_4 }
>
> \m{1 - C_2^^n \tan^2\theta + C_4^^n }
>
> \stopTEXpage
>
Hi,
ConTeXt supports prescripts:
\startTEXpage[offset=1DK]
\m{1 - {}^nC_2\tan^2\theta + {}^nC_4 }
\m{1 - C_2^^n \tan^2\theta + C_4^^n }
\stopTEXpage
If you want them below, use double _.
/Mikael
On Mon, Jan 15, 2024 at 7:45 AM Shiv Shankar Dayal
wrote:
>
> Suppose I want to t
t; > symbols is wheelchair. However, when using that, I just got the string
> > _378 (3.pdf). Source code:
> >
> > ```
> > \usesymbols[fontawesome]
> >
> > \startTEXpage[offset=1pt]
> > \symbol[fontawesome][wheelchair]
> > \stopTEXpa
here, one of the few remaining
symbols is wheelchair. However, when using that, I just got the string
_378 (3.pdf). Source code:
```
\usesymbols[fontawesome]
\startTEXpage[offset=1pt]
\symbol[fontawesome][wheelchair]
\stopTEXpage
```
Is there a problem with my installation?
Additional
chair. However, when using that, I just got the string
_378 (3.pdf). Source code:
```
\usesymbols[fontawesome]
\startTEXpage[offset=1pt]
\symbol[fontawesome][wheelchair]
\stopTEXpage
```
Is there a problem with my installation?
Additional output:
```
% mtxrun --script fonts --list --all --
> pair BEndPoint; BEndPoint = point 1 of B;
> > >> path C; C = AStartPoint..AEndPoint;
> > >>
> > >> p1:=image(
> > >> draw A withcolor red;
> > >> );
> > >>
> > >> p2:=image(draw A; label(lmt_outline [
> >
\HF or \HF[n].
\startTEXpage[offset=1DK]
\dm{
\startnamedmatrix[matrix:bars]
\NC 1 \NC x \NC x^2 \NC \ldots \NC x^{n-1} \NR
\NC 1 \NC y \NC y^2 \NC \ldots \NC y^{n-1} \NR
\HF[3] \NR
\NC 1 \NC z \NC z^2 \NC \ldots \NC z^{n-1} \NR
\stopnamedmatrix
}
\stopTEXp
1.
>>> >
>>> > \mapfontsize[modern][script] [.4]
>>> > \mapfontsize[modern][scriptscript][.2]
>>> >
>>> > \setupbodyfont[modern,12pt]
>>> >
>>> > \startTEXpage[offset=1DK]
>>> > \m{z_{n+1}}
>>> > \stopT
ipt] [.4]
>> > \mapfontsize[modern][scriptscript][.2]
>> >
>> > \setupbodyfont[modern,12pt]
>> >
>> > \startTEXpage[offset=1DK]
>> > \m{z_{n+1}}
>> > \stopTEXpage
>>
>> Strange, here it looks OK. Maybe something that will be solved when
&
l symbol is too big as well as the number 1.
> >
> > \mapfontsize[modern][script] [.4]
> > \mapfontsize[modern][scriptscript][.2]
> >
> > \setupbodyfont[modern,12pt]
> >
> > \startTEXpage[offset=1DK]
> > \m{z_{n+1}}
> > \stopTEXpage
>
> S
ing example the operational
> > symbol is too big as well as the number 1.
> >
> > \mapfontsize[modern][script] [.4]
> > \mapfontsize[modern][scriptscript][.2]
> >
> > \setupbodyfont[modern,12pt]
> >
> > \startTEXpage[offset=1DK]
> &
etupbodyfont[modern,12pt]
>
> \startTEXpage[offset=1DK]
> \m{z_{n+1}}
> \stopTEXpage
Strange, here it looks OK. Maybe something that will be solved when
there is an update then.
/Mikael
___
If your quest
Thank you for your suggestion but in the following example the operational
symbol is too big as well as the number 1.
\mapfontsize[modern][script] [.4]
\mapfontsize[modern][scriptscript][.2]
\setupbodyfont[modern,12pt]
\startTEXpage[offset=1DK]
\m{z_{n+1}}
\stopTEXpage
Le ven. 29 déc. 2023 à
, z_{n+1}=\frac{i}{3}z_n}
you could try something like (here with too small numbers only to show...)
\mapfontsize[modern][script] [.4]
\mapfontsize[modern][scriptscript][.2]
\setupbodyfont[modern,10pt]
\startTEXpage[offset=1DK]
\m{3^{2^3}}
\stopTEXpage
I
nTeXt cannot simply find where the
> converted PDF versions of the zint images are.
>
> If I have the following source in testing-barcodes.tex:
>
> \usemodule[m-zint]
> \starttext
> \startTEXpage[offset=1dk]
> \barcode[alternative=isbnx, text=9783865419026,
stalled (or its path is
unknown to the system), or ConTeXt cannot simply find where the
converted PDF versions of the zint images are.
If I have the following source in testing-barcodes.tex:
\usemodule[m-zint]
\starttext
\startTEXpage[offset=1dk]
\barcode[alternative=isbnx, text=9783865419026, width=
themselves.
Basically one can sign (with some certificate) and then validate.
% sign-001.tex
\setupinteraction[state=start]
\definefield[signature][signed]
\defineoverlay[signature][my signature]
\starttext
\startTEXpage[offset=1ts,frame=on,framecolor=darkblue]
sign: \inframed
[
> >> text = "\KoreanFont 한국어"
> >> ], AStartPoint););
> >>
> >> p5:=image(
> >> label(textext("bāng"), BEndPoint);
> >> draw C withcolor green;
> >> );
> >>
> >> p6:=image(
> >> draw B
dPoint; AEndPoint = point 4 of A;
> > >> path B; B = z5..z6;
> > >> pair BStartPoint; BStartPoint = point 0 of B;
> > >> pair BEndPoint; BEndPoint = point 1 of B;
> > >> path C; C = AStartPoint..AEndPoint;
> >
>> );
> >>
> >> p4:=image(draw A; label(lmt_outline [
> >> text = "\KoreanFont 한국어"
> >> ], AStartPoint););
> >>
> >> p5:=image(
> >> label(textext("bāng"), BEndPoint);
> >> draw C withcolor green;
&g
> >> p5:=image(
> >> label(textext("bāng"), BEndPoint);
> >> draw C withcolor green;
> >> );
> >>
> >> p6:=image(
> >> draw B withcolor blue;
> >> );
&g
% Just for learning :
>> draw TheFrame withpen pencircle scaled .1in withcolor magenta ;
>> draw textext("T="(currentime)) scaled 2 shifted(0,2in) withcolor
>> magenta ;
>> for k=1 upto currentime: draw p[k]; endfor
>> setbounds currentpicture to The
gt; }
>
> \stoptext
> On Nov. 27 2023, at 11:25 pm, Aditya Mahajan wrote:
>
> On Mon, 27 Nov 2023, Fabrice L wrote:
>
> > Hi,
> >
> > It is fun fact very easy to do. You just use \startMPpage (…)
> \stopMPpage multiple times. Here is an example which b
>
> > > Hi,
> > >
> > > It is fun fact very easy to do. You just use \startMPpage (…) \stopMPpage
> > > multiple times. Here is an example which build an animation of a particle
> > > moving according to a Brownian motion.
> >
> > A
e to a metapost drawing. This is
> what I use:
> https://adityam.github.io/context-blog/post/metapost-animation/
> It only works when viewed in acrobat, you can just comment out the animation
> part and wrap it in \startTEXpage .. \stopTEXpage to get multi-page animation.
> Aditya
pass a variable to a metapost drawing. This is what
I use:
https://adityam.github.io/context-blog/post/metapost-animation/
It only works when viewed in acrobat, you can just comment out the animation
part and wrap it in \startTEXpage .. \stopTEXpage to get multi
r documentation for ConTeXt somewhere?
\usesymbols[fontawesome]
\startTEXpage[offset=1ts]
\symbol[fontawesome-solid][times]\quad
\symbol[fontawesome-solid][check]
\stopTEXpage
you can run symb-imp-fonta
[references.border=darkblue]%
\goto{#1}[url(#1)]\stop}
\starttext
\startTEXpage[offset=1dk, align=middle]
\inone{one}\blank
\intwo{two}\blank
\inthree{three}\blank
\stopTEXpage
\chapter[one]{First chapter}
\chapter[two]{Second chapter}
\chapter
}
\starttext
\startTEXpage[offset=1dk, align=middle]
\inone{one}\blank
\intwo{two}\blank
\inthree{three}\blank
\stopTEXpage
\chapter[one]{First chapter}
\chapter[two]{Second chapter}
\chapter[three]{Second chapter}
\stoptext
I see that the directive for link
/21/2023 3:29:22 PM
Subject Re: [NTG-context] Re: Toggling the symbol for the zero-width joiner and
related Unicode control characters
Many thanks, Hans. The method appears to work only for nbsp, not zwj etc.
Here is the updated MWE:
===
\startTEXpage[offset=1em]
\disabletrackers[typesett
e: Toggling the symbol for the zero-width joiner and
related Unicode control characters
Many thanks, Hans. The method appears to work only for nbsp, not zwj etc.
Here is the updated MWE:
===
\startTEXpage[offset=1em]
\disabletrackers[typesetters.directions]
\disabletrackers[typesetters.zwj]
\di
ad a similar mechanism for toggling the
symbols for Unicode control characters but cannot find it.
Does anyone know or recall where the symbol-toggling mechanism is?
If not, what would be the simplest way to implement it?
Here is a MWE (note that the three control chars might be invisible in yo
ymbols for Unicode control characters but cannot find it.
Does anyone know or recall where the symbol-toggling mechanism is?
If not, what would be the simplest way to implement it?
Here is a MWE (note that the three control chars might be invisible in your
email client):
==
\startTEXpag
nyone know or recall where the symbol-toggling mechanism is?
If not, what would be the simplest way to implement it?
Here is a MWE (note that the three control chars might be invisible in your
email client):
==
\startTEXpage[offset=1em]
\definedfont[almfixed at 14pt]
ZWJ:
ZWN
l-toggling mechanism is?
If not, what would be the simplest way to implement it?
Here is a MWE (note that the three control chars might be invisible in your
email client):
==
\startTEXpage[offset=1em]
\definedfont[almfixed at 14pt]
ZWJ:
ZWNJ:
NBSP:
\stopTEXpage
==
In No
]
\enabledirectives[references.border=darkgreen]
\starttext
\startTEXpage[offset=1dk]
\attachment[method=hidden, file=a(b).pdf]
\stopTEXpage
\stoptext
The name in EmbeddedFiles is "a\(b\).pdf".
Sorry for the obscure question, but how can I access this with
"\goto{l
Dear list,
I have the following source:
\setupinteraction[state=start, display=new]
\enabledirectives[references.border=darkgreen]
\starttext
\startTEXpage[offset=1dk]
\attachment[method=hidden, file=a(b).pdf]
\stopTEXpage
\stoptext
The name in EmbeddedFiles is "a\(b\
On 9/4/2023 6:12 PM, Pablo Rodriguez wrote:
Dear list,
after updating to current latest (from 2023.09.03 19:03), packed list
doesn’t seem to work in LMTX:
\starttext
\startTEXpage[offset=1em]
\startitemize[packed]
\item item
\item item
\stopitemize
\stopTEXpage
On 9/4/2023 12:12 PM, Pablo Rodriguez wrote:
Dear list,
after updating to current latest (from 2023.09.03 19:03), packed list
doesn’t seem to work in LMTX:
\starttext
\startTEXpage[offset=1em]
\startitemize[packed]
\item item
\item item
\stopitemize
\stopTEXpage
Dear list,
after updating to current latest (from 2023.09.03 19:03), packed list
doesn’t seem to work in LMTX:
\starttext
\startTEXpage[offset=1em]
\startitemize[packed]
\item item
\item item
\stopitemize
\stopTEXpage
\stoptext
MkIV gets packed lists just right.
Could anyone
I’m afraid that \in{attachment}[foobar] doesn‘t generate a link in your
sample.
Or do you get a link border from the following source?
\setupinteraction[state=start]
\enabledirectives[references.border=green]
\starttext
\startTEXpage[offset=1em]
\attachment[
file={hacker.jpg},
m
his):
\definefontfamily[mainface][rm][DejaVu Sans]
[sl≃style:bf]
\setupbodyfont
[mainface, 100pt]
\starttext
\startTEXpage[offset=1ex]
a {\em b}
\stopTEXpage
\stoptext
Many thanks for your help again,
Pablo
][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX
:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text
]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine, independent from font size.
Could anyone confirm the issue?
Many
e can do
>
> \starttext
>
> \setupframed
> [mathstrikeout]
> [color=darkgreen,
> backgroundcolor=darkred,
> frame=off]
>
> \startTEXpage[offset=4dk,align=flushleft]
> \dm{1+\mathstrikeout[strike:text={what is this?}]{(2x-x)}+2=3+x}
> \blank
> \dm{1+\mathstrike
ce
I don't know what the cancel package gives, but since December 22 or
so, one can do
\starttext
\setupframed
[mathstrikeout]
[color=darkgreen,
backgroundcolor=darkred,
frame=off]
\startTEXpage[offset=4dk,align=flushleft]
\dm{1+\mathstrikeout[strike:text={what is this?}]{(2x-x)}+2=3+x}
\blank
process a file and you should see
> > something like this:
> >
> > As you can see the luatex engine processes the file cont-yes.mkiv and not
> > your document which put as argument to context. Your document is just read
> > by cont-yes.mkiv and at the end of the docume
Carlos,
> On 8/20/2023 6:41 PM, Wolfgang Schuster wrote:
And now it gets even worse, see
https://meeting.contextgarden.net/2021/talks/2021-09-21/starttext.pdf
why \starttext is necessar
And watch how \startTEXpage is defined. It clearly explains why that
works without.
Also watch how \
and at the end of the document ConTeXt inserts an extra \stoptext
which is ignored when your document
is valid (equal number of \starttext and \stoptext).
The bonus \starttext is just there so that we can use \startTEXpage etc
without wrapper and a second bonus is that it catches sloppy coding
% sqtfm=yes]
\showglyphs
\startTEXpage[offset=1em]
\definedfont[texgyretermes-regular*forceyes]
% \definedfont[texgyretermes-regular*forceno]
% \addfeature{forceyes}
abcdefg
\stopTEXpage
==
You may toggle these lines:
\definedfont[texgyretermes-regular*forceyes]
% \definedfont[t
({ "first" })
or
context.usemodule{ "first" }
context.enableinputtranslation()
context.darkgreen()
\stopluacode
\startTEXpage[offset=1em]
\translateinput[Hermes][Idris]
Hermes
\disableinputtranslation
Hermes
\stopTEXpage
===
tex error > tex error on line 14 in
({ "first" })
or
context.usemodule{ "first" }
context.enableinputtranslation()
context.darkgreen()
\stopluacode
\startTEXpage[offset=1em]
\translateinput[Hermes][Idris]
Hermes
\disableinputtranslation
Hermes
\stopTEXpage
===
tex error > tex error on
\startTEXpage[offset=1em]
\translateinput[Hermes][Idris]
Hermes
\disableinputtranslation
Hermes
\stopTEXpage
===
tex error > tex error on line 14 in file ./test-luacode.tex: Undefined
control sequence
\translateinput
[Hermes][Idris]
===
The reason for the er
ection 6 of the manual.
> \startTEXpage[offset=1ex]
> x\vrule height 1fa depth 1fd\relax x % \ascender \descender
> x\vrule height 1sh depth 1sd\relax x % \strutht \strutdp
> x\vrule height 1fc depth 0pt\relax x % \capheight
> \stopTEXpage
>
> you can also run s-sys
Hi Pablo,
I Uploaded an update so you can spend the evening wikifying units ...
see lowlevel manual for the full list
\startTEXpage[offset=1ex]
x\vrule height 1fa depth 1fd\relax x % \ascender \descender
x\vrule height 1sh depth 1sd\relax x % \strutht \strutdp
x\vrule height 1fc
On 8/15/23 21:48, vm via ntg-context wrote:
> [...]
> A different approach is to use \dontleavehmode
In that case, \dorecurse is your friend, such as in:
\starttext
\startTEXpage[offset=10mm, pagestate=start]
\dorecurse{5}{
\dontleavehmode
\framed[frame=off]{\externalfigure[p1-4_4-01-56-
.
There is probably a reason for this to happen, but how to avoid it ?
.Floris
[MWE]
\starttext
\startTEXpage[offset=10mm, pagestate=start]
\startcombination[nx=3, ny=5]
\startcontent\externalfigure[p1-4_4-01-56-25-015.png][height=.2\textwidth,width=.2\textwidth]\stopcontent
\startcontent\externalfigure[p1
Placing identical images in a n x m grid
shows extra space every two rows.
Also the vertical and horizontal spaces are different.
There is probably a reason for this to happen, but how to avoid it ?
.Floris
[MWE]
\starttext
\startTEXpage[offset=10mm, pagestate=start]
\startcombination[nx
[\s!rm] [\s!serif] [latin-modern-designsize]
[\s!default] [\s!designsize=\s!auto]
so [\s!designsize=\s!auto] means there is no explicit call to lmroman8-regular
etc.? Interesting..
Ok, let's try it:
===
\setupbodyfont[modern-designsize]
\startTEXpage[offset=1em]
Test {\tfa Test} {\tfb Test
On 8/15/2023 3:56 PM, Hamid,Idris wrote:
Dear gang,
It seems that ConTeXt does not currently implement optical scaling for Latin
Modern -- at least not by default. For example:
===
\startTEXpage[offset=1em]
Test {\tfa Test} {\tfb Test} {\tfc Test} {\tfd Test} {\tfx Test} {\tfxx Test
Dear gang,
It seems that ConTeXt does not currently implement optical scaling for Latin
Modern -- at least not by default. For example:
===
\startTEXpage[offset=1em]
Test {\tfa Test} {\tfb Test} {\tfc Test} {\tfd Test} {\tfx Test} {\tfxx Test}
\stopTEXpage
===
In the log we have
Dear gang,
Consider the following example:
==
\setupdirections[bidi=global,method=one]
\startTEXpage[offset=1em,width=14in]
\definedfont[almfixed*arabic]
\switchtobodyfont[almfixed*arabic]
\switchtobodyfont[almfixed]
% \addff{arabic}
\startbuffer[]
\startlines
الثَّعْلَبُ
0x043,0.5,true) -- some fake
end
end
local specification = {
name= "idrify",
description = "idrify",
manipulators = {
base = initialize,
node = initialize,
}
}
fonts.handlers.otf.features.register(specification)
\stopluacode
% \def
(and different linebreaking).
> >
> > \showglyphs
> >
> > \startTEXpage[offset=1ex]
> > \ruledhbox{$\overline{OA} = \overbar {OA} = 4.2$}
> > \par
> > \ruledhbox{$\underline {OA} = \underbar {OA} = 4.2$}
> > \par
>
at tug meetings on YT.
The output with Luametatex is correct but Luatex creates a raised bar
(and different linebreaking).
\showglyphs
\startTEXpage[offset=1ex]
\ruledhbox{$\overline{OA} = \overbar {OA} = 4.2$}
\par
\ruledhbox{$\underline {OA} = \underbar
So,
Finally is it a bug in MKIV? It seems you fix some kind of bug in your
messages. Is it true?
> The output with Luametatex is correct but Luatex creates a raised bar
> (and different linebreaking).
>
> \showglyphs
>
> \startTEXpage[offset=1ex]
> \ruledh
tchbox
% \boxyoffset\scratchbox\scratchheight
% \boxorientation\scratchbox\plustwo
% \ht\scratchbox\scratchheight
% \box\scratchbox
% \egroup
% \stopsetups
% \definesymbol
% [iTee]
% [\directsetup{glyph:iTee}]
% \startTEXpage [offset=1ts,wid
cratchbox\scratchheight
\boxorientation\scratchbox\plustwo
\ht \scratchbox\scratchheight
\box\scratchbox
\egroup
\stopsetups
\definesymbol
[iTee]
[\directsetup{glyph:iTee}]
\startTEXpage [offset=1ts,width=2cm]
\ruledhbox {\tfx T \symbol{iTee}} \par
\ruledhbox {T \symbol{iTee}} \par
\ruledhbox {\tf
hbox\scratchheight
> \box\scratchbox
> \egroup
> \stopsetups
> \definesymbol
> [iTee]
> [\directsetup{glyph:iTee}]
> \startTEXpage [offset=1ts,width=2cm]
> \ruledhbox {\tfx T \symbol{iTee}} \par
> \ruledhbox {T \symbol{iTee}} \par
> \ruledhbox {\tfa T \symbol{iTee}} \par
>
ight
\box\scratchbox
\egroup
\stopsetups
\definesymbol
[iTee]
[\directsetup{glyph:iTee}]
\startTEXpage [offset=1ts,width=2cm]
\ruledhbox {\tfx T \symbol{iTee}} \par
\ruledhbox {T \symbol{iTee}} \par
\ruledhbox {\tfa T \symbol{iTee}} \par
\ruledhbox {\bfd T \symbol{iTee}}
\stopTEXpage
Great, will study
tchbox\scratchheight
\box\scratchbox
\egroup
\stopsetups
\definesymbol
[iTee]
[\directsetup{glyph:iTee}]
\startTEXpage [offset=1ts,width=2cm]
\ruledhbox {\tfx T \symbol{iTee}} \par
\ruledhbox {T \symbol{iTee}} \par
\ruledhbox {\tfa T \symbol{iTee}} \par
\ruledhbox
Dear gang,
I. In Context, as is well known, scaling a character is not independent of
switching the font:
===
\startTEXpage[offset=1em]
\definefont[Times][times @ 14pt]
\Times Test \tfx Test
\setupinterlinespace
\Times Test \switchtobodyfont[x]Test
\Times Test \high{Test}
\stopTEXpage
a raised bar
(and different linebreaking).
\showglyphs
\startTEXpage[offset=1ex]
\ruledhbox{$\overline{OA} = \overbar {OA} = 4.2$}
\par
\ruledhbox{$\underline {OA} = \underbar {OA} = 4.2$}
\par
\ruledhbox{$\widetilde {OA} = \widebar {OA} = 4.2$}
\par
: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
overbar.pdf
Description: Adobe PDF document
\startTEXpage[offset=1ts]
$\overbar{OA} = 4.2$
\stopTEXpage
uded pages in an explicit
makeup (as I am now doing)?
\pagefigure[...][...] (no need for \startpagefigure .. \stoppagefigure)
is a combination of \startTeXpage and \externalfigure and you shouldn't
put the command in a makeup environment.
.org/2000/svg;>
\stopbuffer
\starttext
\startTEXpage
\includesvgbuffer[gradient]
\stopTEXpage
\startMPpage
fill unitsquare xyscaled (200,100)
withshademethod "linear"
withs
?
> No, it's an independent feature of the linebreak mechanism. You can run
> this and see how it kicks in
>
> \starttext
>
> \definecolor[ttest][a=1,t=.5]
> \definecolor[rtest][a=1,t=.5,r=1]
>
> \dostepwiserecurse{80}{120}{1}{
> \startTEXpage[of
]
\definecolor[rtest][a=1,t=.5,r=1]
\dostepwiserecurse{80}{120}{1}{
\startTEXpage[offset=1ts]
\startcombination[1*3]
{\startoverlay
{\vtop{\showmakeup[space]\hsize #1mm\ttest
\samplefile{tufte}}}
{\vtop{\showmakeup[space]\hsize #1mm\rtest
1 - 100 of 1098 matches
Mail list logo
